|
HTTP pipelining is a technique in which multiple HTTP requests are sent on a single TCP connection without waiting for the corresponding responses.〔(【引用サイトリンク】title=Hypertext Transfer Protocol (HTTP/1.1): Message Syntax and Routing )〕 The pipelining of requests results in a dramatic improvement in the loading times of HTML pages, especially over high latency connections such as satellite Internet connections. The speedup is less apparent on broadband connections, as the limitation of HTTP 1.1 still applies: the server must send its responses in the same order that the requests were received — so the entire connection remains first-in-first-out〔 and HOL blocking can occur. The asynchronous operation of the upcoming HTTP/2 or SPDY could be a solution for this. Non-idempotent methods like POST should not be pipelined.〔(【引用サイトリンク】title=Connections )〕 Sequences of GET and HEAD requests can always be pipelined. A sequence of other idempotent requests like PUT and DELETE can be pipelined or not depending on whether requests in the sequence depend on the effect of others.〔 HTTP pipelining requires both the client and the server to support it. HTTP/1.1 conforming servers are required to support pipelining. This does not mean that servers are required to pipeline responses, but that they are required not to fail if a client chooses to pipeline requests. ==Implementation status== Pipelining is only supported in HTTP/1.1, not in 1.0. 抄文引用元・出典: フリー百科事典『 ウィキペディア（Wikipedia）』 ■ウィキペディアで「HTTP pipelining」の詳細全文を読む スポンサード リンク
|